@asafpamzn There are too many patches in this pull request and it would be difficult for someone to comment on the changes.

The following document provides more information on how to contribute to CRIU:
https://github.com/checkpoint-restore/criu/blob/criu-dev/CONTRIBUTING.md

I'm implementing a COW-based live migration feature for CRIU that uses userfaultfd write-protection to track memory modifications while the process continues running. The goal is to combine it with the lazy support in order to be able to duplicate a process to remote instance while minimizing downtime compared to traditional dump modes.

I believe Mike Rapoport (@rppt) might be able to provide some advice about the idea.

Thanks @rst0git ,

Since it is a big change I would like to get advice about the general direction before starting to implement. I can provide a design doc if it works better. What is the best path going forward?
Should I consult with @rppt ?

Since it is a big change I would like to get advice about the general direction before starting to implement. I can provide a design doc if it works better. What is the best path going forward?

Creating a GitHub issue with more information about the use-case and why this functionality is important will help us to understand the proposed design.

Should I consult with @rppt ?

There are multiple people in the community that can provide feedback. Mike is a MM maintainer for the Linux kernel and contributed many of the patches that enable post-copy migration with userfaultfd.

Since it is a big change I would like to get advice about the general direction before starting to implement. I can provide a design doc if it works better. What is the best path going forward?

Let's start with a design doc.